Hi all, My queus in my Exchange 2007 hub transport servers are filled by message Spam. The hub stop transmitting and receiving messages. The EdgeTransport.exe is consumming a lot of memory. How can I empty the queues? the command Get-Queue Submission returns an error. thx

1. Stop Exchange Transport 2. Browse to the folder where mail.que is stored(Default Location of mail queue c:\programfiles\Microsoft\Exchange Server\TransportRoles\data\Queue) 3. Delete or move everything there 4. Start the Exchange Transport 5. Open up Queue Viewer, and verify that every thing's cleared..Exchange has now recreated mail.que and associated files like in the beginning of time

Can I also add that the following considerations:1. If the SPAM has a pattern trend, then configure a Transport Rule to drop the offending messages2. Do you have a antivirus/spam product installed on the Hub Transport Servers (or even the free Edge Anti-spam function on HT Servers: http://technet.microsoft.com/en-us/library/bb201691(EXCHG.140).aspx), have an Edge deployment or use third party gateways to secure your perimeter?Stopping the Transport Service and effectively deleting the queue isn't always the best answer, especially if you continue to be attacked and the queue becomes unmanageble and slow within a short amount of time after firing it back up.Oliver

Is there any risk to lose important email? thx

Deleting the queue by stopping Transport Services and then hard deleting the queue database will lose legitimate email yes.If you want manage the queue instead (on top of previous considerations post).Open the Exchange Management Console, go to Toolbox and then Queue Viewer under Mail Flow Tools.You can then view the queues on your selected Hub Transport Servers and select and delete as appropriate. Consider taking the Server out of load balance/NAT for incoming SMTP whilst you perform this.Note you can also use the Exchange Mail Flow Troubleshooter also in this section of the toolbox.Oliver

http://technet.microsoft.com/en-us/library/bb124343.aspxWorking with the Queue Database on Transport ServersThis walks through the steps to move the queue and recover. Its intended for a damaged database, but can work in this scenario as well.As Oliver mentions, do you have anti-spam at the edge?Are you doing recipient filtering against Active Directory as well so you dont accept mail destinted for unknown recipients? That's very important.